Be more systematic about _setjmp vs setjmp.
authorPaul Eggert <eggert@cs.ucla.edu>
Tue, 4 Sep 2012 06:34:19 +0000 (23:34 -0700)
committerPaul Eggert <eggert@cs.ucla.edu>
Tue, 4 Sep 2012 06:34:19 +0000 (23:34 -0700)
commitf3ce84b430c96cf1aeeaa6450415030c9d88b83a
tree9e89edaad9d3531c035407ca9a136dfa125277c0
parentf8abdbaec6ae40cd9f494a837d924b48c2a6363a
Be more systematic about _setjmp vs setjmp.

* alloc.c (test_setjmp, mark_stack):
* image.c (PNG_LONGJMP) [PNG_LIBPNG_VER < 10500]:
(PNG_JMPBUF) [! (PNG_LIBPNG_VER < 10500)]:
(png_load, my_error_exit, jpeg_load):
* process.c (send_process_trap, send_process):
Uniformly prefer _setjmp and _longjmp to setjmp and longjmp.
The underscored versions are up to 30x faster on some hosts.
Formerly, the code used setjmp+longjmp sometimes and
_setjmp+_longjmp at other times, with no particular reason to
prefer setjmp+longjmp.
src/ChangeLog
src/alloc.c
src/image.c
src/process.c